Release 10.1A: OpenEdge Development:
Progress Dynamics Managers API Reference

updateTableViaSDO

This procedure updates the database through the relevant SDO.

Location: af\app\afgenmngrp.i

Parameters:

INPUT pcSdoName AS CHARACTER

The filename of the SDO used in the update.

INPUT pcSdoDescription AS CHARACTER

The description of the SDO.

INPUT pcExtraProperties AS CHARACTER

A CHR(3)-delimited string of additional properties to set in the SDO (see Notes).

INPUT pcUserProperties AS CHARACTER

A CHR(3)-delimited string of additional user properties to set in the SDO (see Notes).

INPUT-OUTPUT TABLE-HANDLE phRowObjUpd

The rowObjUpd table containing records for update.

Returns: See Notes

Notes:

Because this procedure always attempts to run the SDO on the ICF AppServer, no distinction is made between the client and server when running this procedure. If the calling procedure is already running on the server, the value of the gshAstraAppserver handle is that of the SESSION to avoid problems.
This procedure starts the SDO, updates the database, and destroys the SDO after any updates. Any errors are reported back to the calling procedure using the RETURN-VALUE.
The ERROR-STATUS error condition is raised; you should not run this procedure with the NO-ERROR option.
The table handle is returned to the calling procedure in case there are further actions to be performed on it, or post-update data is required. For example, a status that is determined in the SDO.
The extra properties string is a CHR(3)-delimited label, value string. These properties are set in the SDO after initialization.
Examples: See the deletePreTransValidate procedure in ry\obj\rycoilog3p.p.